-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] [linux] [opengl] Use RTLD_LOCAL to prevent LLVM symbol conflict with GLX #1326
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1326 +/- ##
==========================================
- Coverage 85.35% 84.89% -0.47%
==========================================
Files 19 19
Lines 3374 3237 -137
Branches 630 630
==========================================
- Hits 2880 2748 -132
+ Misses 362 357 -5
Partials 132 132
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (with no way to verify..)!
This fixed the same error on my end with opengl enabled. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't clearly remember why I added RTLD_GLOBAL
here, but let's see if everything works :-) Thanks.
I could verify this on my end, just a sec. |
Unfortunately, sth is still going wrong on my end. Please see the log below
|
@Eydcao note that the error message is changed, so you actually encountered another issue, I know why this occur and will fix later. |
Yeah this time at least compute shade appears. So it has reached the glx with the correct llvm version |
Related issue = close #958 close #1100 close #1106 close #1113 close #1325
[Click here for the format server]
Specifying
RTLD_GLOBAL
will expose Taichi-customized LLVM symbols to other modules that may depends on other LLVM versions, e.g. GLX depends on LLVM and cause the issues above.@Eydcao @TroyZhai This issue is finally solved systematically!!! Please confirm that if this PR works when you have time :)